Change the run-time account for Content Studio

Applies to: Content Studio ver. 3.2 and later

Normally there is no need to change the Content Studio run-time account. Doing so will cause Content Studio to stop working due to permission problems. A common reason to change the account is when a stand-alone server has been made a member server in Active Directory and you would enable active directory user accounts to be used in Content Studio. This can be a very time- consuming process since it involves rebuilding of all files in the site's file system at a new location and should be very well planned.

• Create the new account according to the rules for the Content Studio run-time accounts.
  
• Create a new root in the file system for the sites. Under this root create one new entry for each one of the sites on the server.
• Copy all files and the folders ~js and ~images located in the root of the original file location to the new location just created. These file are identical between each site with the exception of the Web.config file. Make sure that you copy the correct one!
• Edit the file permissions of the ~js and ~images folder. Turn off inheritance and set Read access to Everyone and Full Control to Administrators ans SYSTEM.
• Edit the permissions of the new site root folder. Turn off inheritance and make sure that the new runtime account has Full Control.
• Repeat this copying process for each one of the Content Studio sites on the server.
  
• Add the new account as a login i sql-server and make it a member or the db_owner fixed role in all the Content Studio site databases.
• If necessary, remove the old accounts from the logins in sql-server.
  
• Stop Internet Information Server (you can use the command IISReset /stop at the command prompt).
• In IIS Manager, edit the location property of each one of the Content Studio so it now points to the new location configured above.
  
• In Service Manager management snap-in make the Content Studio server service run as this new account.
  
• Run the Site Content Manager application and select one of the sites.
• Edit the Site Path setting to reflect the new file path, make sure the value ends with a \ (backslash). You can edit this value by clicking the Manage Server button.
• Rebuild the files and make sure you have set the "Include binary files with synchronization" option.
• After that all files have been built continue with the rest of the sites until you have gone through all of them.
  
• Restart IIS (you can use the command IISReset /start at the command prompt) and verify the your sites are all working properly.
• After testing that the sites are working you can remove all of the files and folders of the old location.

This is an advanced action in Content Studio and should not be performed by unexperienced users. If you are the least un-certain what to do contact a Content Studio developer or partner.